Skip to content

fix: align profile environment classification with actual support level#243

Open
SemTiOne wants to merge 1 commit into
RonaldHensbergen:mainfrom
SemTiOne:fix/environment-classification
Open

fix: align profile environment classification with actual support level#243
SemTiOne wants to merge 1 commit into
RonaldHensbergen:mainfrom
SemTiOne:fix/environment-classification

Conversation

@SemTiOne

Copy link
Copy Markdown
Collaborator

Pull Request

Summary

_infer_profile_class read profile["name"] (doesn't exist, real path is metadata.name), so every profile silently classified as "local" regardless of declared environment. Fixed to read metadata.environment. Added schema enum, a productionSuitable module flag, and CDS-SEC-073 to catch a non-local profile using a dev-only module; fixed the vault profile/module, which had exactly that contradiction.

closes #217

Type Of Change

  • Bug fix
  • Feature
  • Refactor
  • Docs
  • Test only

User Impact

Security rules using profileClasses now evaluate against the real declared environment instead of always seeing "local".

Validation

136 passed, 1 skipped.

python -m unittest discover -s tests -p "*.py"

Checklist

  • Tests added or updated
  • Docs updated (README or docs)
  • No secrets committed
  • Generated artifacts excluded from git

Does NOT resolve

metadata.environment isn't enforced by validate_profile_shape; invalid/missing values silently default to "local". Fixing that touches ~40 fixtures across 4 test files (separate issue).

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.

Align profile environment classification with actual support level

1 participant