Add a bit of debug context

[theodore-s-beers]

I think it could be helpful to know at this point that what is being printed is the exit code of the preceding curl command. It should be 0, of course, but we saw another value (60) while troubleshooting an issue with an endpoint. It took me a while to figure out what it was referring to.

Summary by Sourcery

Enhancements:

• Add context to debug output by specifying that the printed value is the curl command's exit code.

[sourcery-ai]

Reviewer's Guide by Sourcery

The change adds more descriptive debug output in a shell script by clarifying that a printed value represents a curl command's exit code. This improves troubleshooting by making the debug output more self-explanatory.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Enhanced debug output clarity in shell script	Modified echo statement to explicitly indicate the value being printed is a curl exit code	repository/docker/entrypoint_authz.sh

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @theodore-s-beers - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[JoshuaSBrown]

@theodore-s-beers, thanks for creating the PR. We should probably work to wrap all the print statements behind a debug flag at some point but this is an improvement.

[theodore-s-beers]

@JoshuaSBrown, should I add an entry to the changelog?