Will Thames

My view is that making namespace non-optional is a safeguarding feature, not a bug, although one could make the same argument for context too (we actually have a context checker...

@elafontaine I'd probably support an `enforce_namespace` which defaults to true - you could then use `enforce_namespace: false` - at that point how it works is not something I'm too fussy...

``` - name: check current kubernetes cluster command: kubectl config current-context changed_when: false register: kubectl_current_context check_mode: no tags: always ignore_errors: yes # this task fails on in-cluster nodes failed_when: no...

If you want to add an `enforce_namespace` flag, the main tasks would be to write the code (including documenting the new option), and add some tests under molecule/default to ensure...

I just recommend not doing that Having a simple task loop over resource manifests means that you get a named task per resource with a proper diff (that works with...

I've updated this PR to use a better check now

Building against latest JMC I had to make a few source changes (as well as the more obvious class changes - which aren't reflected here as I do a `sed...

I'm not sure about the change to commercial features - in testing with a Java 10, I'm not sure how you can run JFR against a JVM that doesn't have...

circleci relies on tar being available to attach workspaces: > tar utility is not present in this image but it is required. Please install it to have workflow workspace capability....

/close I'm unwilling to maintain a PR with no apparent interest - if anyone does want me to rebase this other than a friendly robot, let me know.