Skip to content

ci(high/easy): validate both environment templates for duplicate keys #528

Closed

Description

@karagozemin

Goal

Add a small static check for duplicate names and unsafe secret-shaped values in root and web .env.example files.

Acceptance criteria

  • The change is covered by a focused automated check.
  • Existing behavior remains unchanged outside this scope.
  • Any new configuration is documented briefly.

Activity

  1. added
    help wantedExtra attention is needed
    area: ciContinuous integration and developer tooling
    priority: highUrgent work with high project or security impact
    securitySecurity, supply-chain, and repository-hardening work
    on Oct 22, 2026
  2. Isaacayomide28 commented on Oct 22, 2026

    @Isaacayomide28

    @Isaacayomide28 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi maintainer, I can work on this issue, please assign

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Isaacayomide28 to this issue.

  3. emirykl commented on Oct 22, 2026

    @emirykl
    Contributor

    @emirykl has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hey, I want to take that issue

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @emirykl to this issue.

  4. krsnak commented on Oct 22, 2026

    @krsnak

    @krsnak has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi, I’d like to work on this.

    I’ll add a static CI check for duplicate keys and unsafe secret-like values in both root and web .env.example files. I’ll include focused automated tests and briefly document the validation without changing existing behavior.

    Thanks!

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @krsnak to this issue.

  5. ect2000 commented on Oct 22, 2026

    @ect2000

    @ect2000 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I reviewed main (df3e368), both .env.example files and the existing static-check scripts. The root and web templates currently have no duplicate keys, so this should be a preventive guard rather than a claim that today's templates are broken.

    After assignment, I would add a small static checker that detects duplicate names within each template and unsafe secret-shaped values without executing or expanding environment content. It would distinguish documented placeholders/public identifiers from actual secret material and report file/key/line without echoing values. Fixture tests would cover comments, blank lines, quoted values, duplicates and safe versus unsafe samples. I would wire it into CI and document the command, coordinating with the other guard PRs.

    I'll keep a focused PR against main and run the checker tests plus relevant existing checks. Source inspection only; I'll wait for official assignment before implementation.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @ect2000 to this issue.

  6. drips-wave commented on Oct 22, 2026

    @drips-wave

    Congratulations, @emirykl! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @emirykl: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  7. grantfox-oss commented on Oct 22, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @emirykl's PR #550 was approved and merged by @karagozemin.

    🏆 @emirykl: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,022 total points). Track your full progress on GrantFox.

    👏 Great work, @emirykl! Keep contributing to Sub-Rosa-Issue.

  8. drips-wave commented on Oct 22, 2026

    @drips-wave

    This issue has been completed by @emirykl as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @emirykl: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssue proposed for the Drips Stellar Wave programarea: ciContinuous integration and developer toolinggood first issueGood for newcomershelp wantedExtra attention is neededpriority: highUrgent work with high project or security impactsecuritySecurity, supply-chain, and repository-hardening work

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions