I noticed that ax apply -a team-a -f workspace.yaml creates the workspace in default when the manifest doesn't set metadata.atespace.
For example:
apiVersion: ax.io/v1alpha1
kind: Workspace
metadata:
name: atespace-example
spec: {}
The command succeeds, but the workspace ends up in default instead of team-a. I reproduced this on 099f24a using the actual CLI against a local AX gRPC server with an in-memory store, and checked the store directly to confirm.
The CLI parses -a, but doesn't pass it to runApply. I'd expect the flag to supply the atespace when the manifest leaves it out.
I noticed that
ax apply -a team-a -f workspace.yamlcreates the workspace indefaultwhen the manifest doesn't setmetadata.atespace.For example:
The command succeeds, but the workspace ends up in
defaultinstead ofteam-a. I reproduced this on099f24ausing the actual CLI against a local AX gRPC server with an in-memory store, and checked the store directly to confirm.The CLI parses
-a, but doesn't pass it torunApply. I'd expect the flag to supply the atespace when the manifest leaves it out.