-
Notifications
You must be signed in to change notification settings - Fork 307
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
Typos, win compatibility, and other small fixes #426
Changes from all commits
defc351
84f9442
a684513
607fb4d
be76b82
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,7 @@ | |
|
||
set -e | ||
|
||
FULL_SERVICE_NAME="env-${PROJECT_NAME}-${ENV_STAGE}-$2"; | ||
FULL_SERVICE_NAME="env-${PROJECT_NAME}-${ENV_STAGE}-$1"; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This change is breaking the ssm-editor by placing the script name instead of the given service name. It leads to setting the invalid path in the SSM Parameter Store, for example: There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Interestingly, I had a different experience and was only able to get the right paths on the SSM parameter store with $1. But some user in discord checked out my branch and had the opposite issue and had to revert to $2. So please leave it as $2 for now and when I test the deploy again I can look further into the issue. |
||
CHAMBER_KMS_KEY_ALIAS="${PROJECT_NAME}-${ENV_STAGE}-main" | ||
|
||
CHAMBER_KMS_KEY_ALIAS="${CHAMBER_KMS_KEY_ALIAS}" /bin/chamber export "${FULL_SERVICE_NAME}" \ | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -38,13 +38,14 @@ COPY $SRC_CORE_PATH/package.json $DEST_CORE_PATH/ | |
COPY $SRC_WORKERS_PATH/package.json $DEST_WORKERS_PATH/ | ||
COPY tsconfig* $APP_PATH/ | ||
COPY $SRC_CLI_PATH $DEST_CLI_PATH/ | ||
RUN pnpm install --include-workspace-root --frozen-lockfile --filter=workers... --filter=cli... | ||
|
||
COPY nx.json tsconfig* jest* babel* .eslintrc* .prettier* .eslintrc* $APP_PATH/ | ||
COPY $SRC_CORE_PATH $DEST_CORE_PATH/ | ||
COPY $SRC_WORKERS_PATH $DEST_WORKERS_PATH/ | ||
RUN chmod +x $DEST_WORKERS_PATH/scripts/*.sh | ||
|
||
RUN pnpm install --include-workspace-root --frozen-lockfile --filter=workers... --filter=cli... | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you explain the reason of changing the order of commands? Basically in this way it will install all pnpm deps on every source code change (it will not use cache for this) and we should avoid this There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So in my experience, if I don't move it, it builds successfully but it has the wrong modules and can not find the module serverless. I thought it was because There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was able to reproduce right now.
|
||
|
||
ENV PYTHONPATH=/pkgs/__pypackages__/3.9/lib \ | ||
PATH=$PATH:/pkgs/__pypackages__/3.9/bin | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so as windows might loose the executable permission (discussed on discord). It is also done in the
workers/Dockerfile
so it's not that alien.