Errors are generated in /var/log/st2/st2rulesengine.log even though the rule is run successfully with out issues.
# st2 --version
st2 3.2.0, on Python 2.7.5
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.8 (Maipo)
Installed with Puppet module
As a microk8s user on Windows/Mac, I want to be able to use a standard kubectl for all my K8s instances that run on my machine.
A solution to that would be to have the installers detect any pre-existing kubeconfig files in the system and automatically append the microk8s context to them. Essentially, the installers need to automate this procedure: https://kubernetes.io/docs/tasks/access-applic
I’m trying to use a Chart Repository by external Nexus, but I’d a problem in pipeline when I’m using the command:
jx step helm release
When this command do the upload chart file, my $CHART_REPOSITORY is changing and including the /api/charts
+ jx step helm release --verbose
DEBUG: Using helmBinary helm with feature flag: template-mode
DEBUG: Initialising Helm 'i
Add field/label "LIVE For:" to show how much time the Revision was LIVE. Currently when a user clicks on the "History and Rollback", it shows all past Revisions and when it was triggered and completed and also displays the amount of time for which that Revision was LIVE. But it does not mention what these timings/durations are for (as shown in the attached screenshot where it shows dur
git-tar needs to clone with a unique path (including branch)
git-tar should clone to a path like: /tmp/owner/repo/branch to avoid conflicts
It clones to:
func clone(pushEvent sdk.PushEvent) (string, error) {
workDir := os.TempDir()
destPath := path.Join(workDir, path.Join(pushEvent.Repository.Owner.Login, pushEvent.Repository.Nam
https://github.com/google/starlark-go/blob/master/doc/spec.md
It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.
Like in #137 we should provide build context information.
it seems older versions of Nginx could be cutting public ingress endpoints. Prescribe from deployment steps 1.24.7 tested version or higher to avoid this issue.
related: #144
In each of the top level commands - az boards, az pipelines, az repos, az artifacts and az devops, we include the line indicating that this command is a part of azure-devops extension. In addition to this, we need to include the link out to the documentation - https://docs.microsoft.com/en-us/azure/devops/cli/?view=azure-devops as well.
Things remaining to be updated since the redesign
Final status table should resemble status-progress table and helm final table with all resources with pods listed. Do not print child resources (too verbose).
A few unit tests are broken in the logs microservice (referenced in this forked repo: suryajak/jazz@6b5afc0) which will need to be fixed once this is merged to master.
Expected behavior: [What you expect to happen]
It would be much more convenient if one could reuse existing IAM policies (custom or managed) and just pass a list of ARNs that would be attached to the Runner's roles
Hello,
I tried to use /bin/terraform-docs.awk to generate documentation with terraform-docs.
An error occured with this variable from provider aws, resource "aws_ecs_service", property "ordered_placement_strategy" :
variable "ordered_placement_strategy" {
type = list(object({
type = string
field = string
}))
description = "Ordered task placement strategy on EC2 inst
Some of the simulators on my machine are unavailable. For instance, the iPad Pro 11 inch on iOS 12.2 is not available because I have not installed the iOS 12.2 simulator.
-- Unavailable: com.apple.CoreSimulator.SimRuntime.iOS-12-2 --
iPhone 5s (739BB7D5-8286-4689-A851-B4BA054B62C6) (Shutdown) (unavailable, runtime profile not found)
iPhone 6 Plus (8D83D9CF-F3E4-4E0B-91CE-B5B61118
As the sole active maintainer, I'm looking for co-maintainers for the project to push features faster.
Please ping me if you're interested.
It'd be awesome if you have already contributed to the project and interested. Otherwise, there would be a brief probation period after starting contributing to the project.
because there is a slight (10-20mins) delay between a push to the repo, and the availability of all its images on docker hub, users should use = r-lib/actions@ref (ideally a release), because a floating reference or even one to master might break sometimes and in really hard-to-understand ways.
Whenever someone would push to the master branch on this repo, a floating ref to master would
Add a description, image, and links to the cicd topic page so that developers can more easily learn about it.
To associate your repository with the cicd topic, visit your repo's landing page and select "manage topics."
The second example in section 1.1 says:
expect(result.approved).to.be.false;It should be:
expect(result.approved).to.be.true;(I'm guessing you made it false so you could simulate the error output in the next picture.)