Skip to content

Add e2e test for [Bug] kubectl apply on crane output directory fails on first run due to alphabetical file ordering #558

Description

@istein1

Please add the below test to cover fix #525 for bug #266:

Given: exported namespace with Role and RoleBinding
When: crane apply --ordered (via CLI binary)
Then:
- Output filenames have numeric prefixes (300_Role_, 310_RoleBinding_)
- kubectl apply -f output/resources// succeeds on first run

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status
Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions