Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gen3 Monthly Release 2022.06 genomel.bionimbus.org 1655919062 #4778

Conversation

PlanXCyborg
Copy link
Contributor

Applying version 2022.06 to genomel.bionimbus.org

@PlanXCyborg PlanXCyborg requested review from trevars and a team as code owners June 22, 2022 17:31
@PlanXCyborg
Copy link
Contributor Author

genomel.bionimbus.org/manifest.json

Deployment changes

Breaking changes

  • fence
    • URL Signing when no_force_sign query param is provided: Previously Fence would make a decision based off if the data was public and no_force_sign provided. Fence will now NEVER sign if no_force_sign is provided (since the concept of "public" data has been abstracted out of Fence. Data access - public or not - is the sole responsibility of the policy engine). In other words, if no_force_sign is provided at the API level, Fence will respect that regardless of whether the resulting URL will actually work. The default Fence behavior should remain the same. chore(jupyter-nde1.1.0) #988 (Feat/passport fence#964)

@m0nhawk m0nhawk closed this Jul 31, 2022
@m0nhawk m0nhawk deleted the chore/apply_202206_to_genomel_bionimbus_org_1655919063 branch July 31, 2022 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants