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

chore: Pipeline Refactor #254

Merged
merged 12 commits into from
Apr 30, 2024
Merged

Conversation

williamputraintan
Copy link
Member

  • Change stage ConstructId name
  • Migrate build notification to alerts-build
  • Change AccountName to AppStage name for consistency

@williamputraintan williamputraintan self-assigned this Apr 26, 2024
@williamputraintan williamputraintan linked an issue Apr 26, 2024 that may be closed by this pull request
@victorskl
Copy link
Member

reviewing...

@victorskl
Copy link
Member

Ah ok, this one is refactor. At least, #250 #115 merge first. The rest branches have to rebase. Let check with the team.

@williamputraintan
Copy link
Member Author

Happy to merge this after those PR are merged!

@williamputraintan
Copy link
Member Author

As this require redeployment, I am also happy to wait if anyone has any objection and wanted to postpone this for later.

Copy link
Contributor

@raylrui raylrui left a comment

Choose a reason for hiding this comment

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

LGTM!

@victorskl
Copy link
Member

@alexiswl This refactor PR can go? And, so that we all follow up rebase onto main after, ok?

@alexiswl
Copy link
Member

Sure

@raylrui
Copy link
Contributor

raylrui commented Apr 29, 2024

Hi @williamputraintan the conflict comes from our talk before, of the account id alias.

@williamputraintan
Copy link
Member Author

Redeploying ...

@reisingerf
Copy link
Member

Not sure if it makes sense to include the following here, but we discussed the option to retrieve constants given a stage rather than using individual constants for that.

E.g. we define 3 constants to look up the ica token here.

Then consumers have to decide which one to use for each stage when defining their config, like here.

We could make that simpler with a common function in the constants that works out which parameter to return given the stage. Something like:
getIcav2AccessTokenSecretName(stage: AppStage)

It would make the consumer config easier and independent of stage definition/changes.

What do you think?

@williamputraintan
Copy link
Member Author

Yeah, think make sense as well to include here. Will follow the pattern with the accountId

@williamputraintan williamputraintan merged commit 1ee5092 into main Apr 30, 2024
2 checks passed
@williamputraintan williamputraintan deleted the chore/233-refactor-pipeline branch April 30, 2024 02:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

chore: CodePipeline Stage name refactor
6 participants