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

AWS Marketplace Configuration #403

Open
wants to merge 83 commits into
base: main
Choose a base branch
from
Open

AWS Marketplace Configuration #403

wants to merge 83 commits into from

Conversation

deathtenk
Copy link
Contributor

This adds a separate marketplace cloud formation configuration for LRSQL (with plans to eventually make this the default configuration for LRSQL deploys marketplace or not).

on:
push:
tags:
- 'v*.*.*' # Enforce Semantic Versioning
Copy link
Member

Choose a reason for hiding this comment

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

have you confirmed what happens if we overwrite a tag? That is something that happens on occasion.

contents: read # required to checkout the code from the repo
steps:
- name: Install JQ
run: sudo apt update && sudo apt install -y jq
Copy link
Member

Choose a reason for hiding this comment

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

im not seeing where this is utilized

Copy link
Member

Choose a reason for hiding this comment

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

nevermind, i see it in the sh. Is this usually how we install shell deps?

@@ -0,0 +1,224 @@
AWSTemplateFormatVersion: '2010-09-09'
Copy link
Member

Choose a reason for hiding this comment

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

should i assume this is identical to old vpc? if so do we need the dupe?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it is identical I just duped for consistency, but duping here isn't necessary.

@@ -0,0 +1,161 @@
AWSTemplateFormatVersion: "2010-09-09"
Copy link
Member

Choose a reason for hiding this comment

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

is this whole template just an abstract password generator for use in other templates? It seems like it asks for a path(s), and then CREATES the passwords in SSM? Just kind of skips anyone having to actually go in there i guess...

@@ -0,0 +1,39 @@
AWSTemplateFormatVersion: '2010-09-09'
Copy link
Member

Choose a reason for hiding this comment

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

so im guessing this one and the next one are more for US not for the actual client deployment?

Description: Version of SQL LRS to pull from Mapping of AMIs
Type: String
AllowedValues:
- v0713
Copy link
Member

Choose a reason for hiding this comment

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

woof, this is the best they can do with semver? I can see this being an issue down the line...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

well the results of the amibuilder are just ami IDs, what im doing here is mapping from semver->region->ami ID. Unfortunately this does mean this template requires manual updates of those mappings for every release.

!Join [":", [!Ref "SecretStackName", "DBMasterUsername"]]
MasterPasswordPath:
Fn::ImportValue:
!Join [":", [!Ref "SecretStackName", "DBMasterUserPasswordPath"]]
Copy link
Member

Choose a reason for hiding this comment

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

cool

Resource: "*"

IngressRuleLambda:
Type: AWS::Lambda::Function
Copy link
Member

Choose a reason for hiding this comment

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

I am unclear on the role of this fn

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.

3 participants