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

Add "env_label" override to BaseProjectConfig.get_stage_config #15

Merged
merged 1 commit into from
Jul 16, 2024

Conversation

njmei
Copy link
Collaborator

@njmei njmei commented Jul 16, 2024

When wanting to deploy stages outside of a CodePipeline context there will still be a need to provide a env_label.

For additional context for why this is needed see the second commit for:
https://github.com/AllenInstitute/merscope-analysis-cloud-pipeline/pull/30

@njmei njmei requested a review from rpmcginty July 16, 2024 03:07
default_config = create_stage_config()

default_config_overrides = {
EnvType.DEV: {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But this is a nested mapping with the key as env type, so adding this capability seems unnecessary, right? Or is this just an env label override

@rpmcginty rpmcginty self-requested a review July 16, 2024 17:16
When wanting to deploy stages outside of a CodePipeline context
there will still be a need to provide a `env_label`.
@njmei njmei force-pushed the fix-get-stage-config branch from aadc219 to a911049 Compare July 16, 2024 17:31
@njmei njmei merged commit e2bca2d into main Jul 16, 2024
4 checks passed
@njmei njmei deleted the fix-get-stage-config branch July 16, 2024 19:03
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