Skip to content

fix: make cdk/destroy.sh executable - #81

Open
bcfmtolgahan wants to merge 1 commit into
aws-samples:mainfrom
bcfmtolgahan:fix/destroy-sh-executable-bit
Open

bcfmtolgahan wants to merge 1 commit into
aws-samples:mainfrom
bcfmtolgahan:fix/destroy-sh-executable-bit

Conversation

@bcfmtolgahan

Copy link
Copy Markdown

Issue #, if available: n/a

Description

cdk/destroy.sh is committed as 100644 in both scaled-execution-containers and agentic-atx-platform, while deploy.sh sitting next to it is 100755:

100755 agentic-atx-platform/cdk/deploy.sh
100644 agentic-atx-platform/cdk/destroy.sh
100755 scaled-execution-containers/cdk/deploy.sh
100644 scaled-execution-containers/cdk/destroy.sh

Four places in the docs tell you to run it directly, so on a fresh clone you get permission denied:

scaled-execution-containers/README.md:391      ./destroy.sh
scaled-execution-containers/cdk/README.md:292  ./destroy.sh
scaled-execution-containers/cdk/README.md:431  ./destroy.sh
agentic-atx-platform/cdk/README.md:69          ./destroy.sh

Worth noting so it does not look like an oversight on my side: container/entrypoint.sh, download-source.sh and upload-results.sh are also 100644, but container/Dockerfile:140 runs chmod +x /app/*.sh at image build, so those are fine as they are. destroy.sh has no equivalent step anywhere - it is meant to be run by hand.

Mode change only, no content changes.

Testing

git ls-files -s before and after; bash -n on both files still passes.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Both destroy.sh files are committed 100644 while deploy.sh next to them
is 100755. The READMEs tell you to run them directly:

    scaled-execution-containers/README.md:391      ./destroy.sh
    scaled-execution-containers/cdk/README.md:292  ./destroy.sh
    scaled-execution-containers/cdk/README.md:431  ./destroy.sh
    agentic-atx-platform/cdk/README.md:69          ./destroy.sh

which fails with permission denied on a fresh clone.

The container scripts are also 100644 but Dockerfile:140 does
chmod +x /app/*.sh at build time, so those are fine. destroy.sh has no
equivalent step - it is meant to be run by hand.

Mode change only, no content.
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.

1 participant