Checklist:

• [ x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• [ x] I've included steps to reproduce the bug.
• [ x] I've pasted the output of argocd version.

Describe the bug

Values from an Application CRD values block that overrides values from value files are not visualized under the App Details -> Parameters -> Parameters section.

**To Repro

Spug运维平台在过去的公司里稳定运行3年以上，开源的大部分代码也是基于稳定版本之上，为了增加更多用户在企业使用的信心，如您愿意，请将您在企业中使用Spug的案例展示给我们，请在该issue页面提供您的使用案例，提交格式：企业名称 + 公司官网地址。官网地址为可选项，您可以直接提供企业名称即可。

此外，您也可以通过其他渠道如QQ、微信、邮件的方式联系项目作者提供使用案例。

征集长期有效，感谢大家支持！

Spug部分案例：

• 上海家谐网络科技有限公司
• 上海爱上慧家信息技术有限公司
• 南京白鸥网络技术有限公司
• 杭州中艺实业股份有限公司
• [北京步鼎方舟科技有限公司](http://

During the setup process, Cilium addon disables the cni.yaml file for microk8s. This causes cluster join to fail due to CNI autodetection. This code path has plenty of comments about Calico specific operations, so it seems that Cilium needs some work on this front.

Apr 11 14:04:43 wanted-wolf microk8s.daemon-cluster-agent[1598267]: Waiting for access to cluster. [2021-04-11 14:04:43,340] E

SUMMARY

I just faced an embarrassed problem that command st2 action list keeps return 503.

I tried st2 --debug action list and the result in line HTTP_PROXY(uppercase) was empty. This mislead me that the proxy info was set(which is not).

I finally found that the root cause is a lowercase http_proxy env variable was set in the system.

So I think it maybe more friend

Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

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.

Howdy. I have a restriction in an environment that prevents wide open egress AWS Security Group rules from being applied (automation actually reverses what this module sets). Each time I apply this rule the automation undoes this, so we get repeating change-in-place loops from TF apply to apply. I'd rather manage this via other means - like using the default SG for the VPC. Is this possible? Or am