Repository navigation
DO-2058: expose project, org and workspace titles to AIO app deploy hooks - #196
Draft
tmthrgd-aligent wants to merge 1 commit into
Draft
tmthrgd-aligent wants to merge 1 commit into
tmthrgd-aligent wants to merge 1 commit into
Conversation
aio-commerce-lib-app's post-app-deploy hook builds the installation action's appData from the AIO config keys project.title, project.org.name and project.workspace.title. The action's schema requires every appData field to be a non-empty string, but the deploy step never set these, so in CI the upgrade request is rejected once the x-gw-ims-org-id header (DO-2058) is in place. Map new AIO_PROJECT_TITLE, AIO_PROJECT_ORG_NAME and AIO_PROJECT_WORKSPACE_TITLE variables into the deploy step and document them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tmthrgd-aligent
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
aio-commerce-lib-app's post-app-deploy hook builds the installation action's appData from the AIO config keys project.title, project.org.name and project.workspace.title. The action's schema requires every appData field to be a non-empty string, but the deploy step never set these, so in CI the upgrade request is rejected once the x-gw-ims-org-id header (DO-2058) is in place.
Map new AIO_PROJECT_TITLE, AIO_PROJECT_ORG_NAME and AIO_PROJECT_WORKSPACE_TITLE variables into the deploy step and document them.
Description of the proposed changes
Screenshots (if applicable)
Other solutions considered (if any)
Notes to PR author
Notes to reviewers
ℹ️ When you've finished leaving feedback, please add a final comment to the PR tagging the author, letting them know that you have finished leaving feedback
Time Tracking
ABC-xxx: code review, select project XXXX