Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address #59 #60

Merged
merged 3 commits into from May 5, 2017
Merged

Address #59 #60

merged 3 commits into from May 5, 2017

Conversation

xiaomi7732
Copy link
Member

This change expose an easy way to support .NET Core application users to initialize AI.Kubernetes in a tradition way.

@msftclas
Copy link

msftclas commented May 5, 2017

@xiaomi7732,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@@ -1,6 +1,6 @@
namespace Microsoft.ApplicationInsights.Kubernetes
{
internal interface IK8sEnvironment
public interface IK8sEnvironment
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why make this public?

Also is it common for public APIs of Kubernetes to short-call them K8s? For example I would rather have EnableApplicationInsightsFoKubernetes instead of EnableK8s

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Good catch. Reverted.
  2. K8s:
    image

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed - I feel APIs are formal things - let's use a formal name.

@xiaomi7732 xiaomi7732 merged commit f4b59b3 into develop May 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants