Deployment configuration for artifacts associated with the build, bundle, and test validation workflow.
While creating an OpenSearch distribution all of the OpenSearch components are built, then bundled together, and finally tested. The intermediate components should always be available for repeatability and to make sure that a build node death is recoverable.
Artifacts should all be available via ci.opensearch.org to connect them via a single domain a CI instance specific identifier added to the url and traffic directed from the central CDN.
- Requires an IAM Role for the context of the build agent
- Requires NPM to be installed
- Install CDK using
npm install -g aws-cdk
- Install project dependencies using
npm install
from this project directory - Configure aws credentials
- Deploy with
cdk deploy
npm run build
compile typescript to js, run lint, run testsnpm run watch
watch for changes and compilecdk deploy
deploy this stack to your default AWS account/regioncdk diff
compare deployed stack with current statecdk synth
emits the synthesized CloudFormation template
Standard deployment for fresh accounts can be done with cdk deploy BuildArtifactDev --parameters buildAgentRoleArn=arn:aws:iam::336984078605:role/JenkinsStackDev-MainNodeInstanceRole6FA3C5C9-1PQFWOWDYN42U
If the account needs migration from the cloudformation script that was previously used, cdk deploy ExistingBuildArtifact --parameters buildAgentRoleArn={ROLE_ARN} --parameters buildBucketArn={BUCKET_ARN}
. During that deployment the existing roles will be updated and there will be manual follow up steps, see the cloudformation output.
- Parameters:
- buildAgentPrincipleArn [string] The principle arn of the build agent
- buildBucketArn [string] If there was an existing S3 bucket, the bucket name