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

Implemented SequenceRunManager app deployment #155

Merged
merged 2 commits into from
Mar 18, 2024

Conversation

victorskl
Copy link
Member

@victorskl victorskl commented Mar 15, 2024

  • Added Shared API Gateway as stateful resource
  • Introduced param constants that go across stateful & stateless
  • Rearranged Python dependencies into deps directory
  • Removed no longer used constants
  • Removed now deprecated API Gateway Alpha constructs
  • Updated CDK nag validation accordingly

Resolves #139

* Added Shared API Gateway as stateful resource
* Introduced param constants that go across stateful & stateless
* Rearranged Python dependencies into deps directory
* Removed no longer used constants
* Removed now deprecated API Gateway Alpha constructs
* Updated CDK nag validation accordingly

Resolves #139
@victorskl
Copy link
Member Author

Anybody else pls feel free look into and chime in, if any.

Copy link
Member

@williamputraintan williamputraintan left a comment

Choose a reason for hiding this comment

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

LGTM

import { SHARED_HTTP_API_ID } from '../../../../config/param';
import { CorsHttpMethod, HttpApi } from 'aws-cdk-lib/aws-apigatewayv2';

export class SharedApiGatewayConstruct extends Construct {
Copy link
Member

Choose a reason for hiding this comment

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

Is the idea to reuse this for all microservices? For some reason I thought the API gateway would be stateless?

Copy link
Member

Choose a reason for hiding this comment

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

Yes, agreed. Maybe refactor it out as a "common" construct that can be reused in (stateless) stacks?

Copy link
Member

Choose a reason for hiding this comment

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

Possibly to put the construct directly on the top level of the stateless stack instead?

https://github.com/umccr/orcabus/blob/feature/pipeline-chores/lib/workload/orcabus-stateless-stack.ts#L53-L60

Copy link
Member Author

Choose a reason for hiding this comment

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

Sound good, folks. I will move it back into its own service for now.

The common construct sound like the plan. But let do that a little bit down the track - until we get to the point where we can collect few use cases to generalise. Then, we shall refactor their commonality from the specificness.

Copy link
Member Author

Choose a reason for hiding this comment

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

Have moved the APIGW into the service boundary. Pls see, if any.

@victorskl
Copy link
Member Author

@brainstorm @williamputraintan Heads up. This PR removes the Alpha constructs importing (which is deprecated upstream) and, they are available now in the main cdk library. i.e. It can be 1-1 replace import:

from @aws-cdk/aws-apigatewayv2-alpha to aws-cdk-lib/aws-apigatewayv2

@victorskl
Copy link
Member Author

Merging...

@victorskl victorskl merged commit 8b49a71 into main Mar 18, 2024
2 checks passed
@victorskl victorskl deleted the deploy-sequence-run-manager branch March 18, 2024 07: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.

Deployment go ahead with sequence_run_manager service
4 participants