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

hostname support wildcard form #26918

Merged
merged 10 commits into from
Feb 9, 2022

Conversation

XiaofeiCao
Copy link
Contributor

fix #26885

@XiaofeiCao XiaofeiCao marked this pull request as ready for review February 8, 2022 08:31
this.innerModel().withHostname(null);
// future work: add hostname instead of replacing
if (hostname == null) {
this.innerModel().withHostNames(null);
Copy link
Member

Choose a reason for hiding this comment

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

Are we allowed to have no hostname in listener?

Ideally if we want to clear a hostname, code should provide a withoutHostname in update flow.

@@ -20,6 +20,8 @@
interface WithHostname<ReturnT> {
/**
* Specifies the hostname to reference.
* The hostname supports wildcard format, e.g. "*.contoso.com", but is available only for
Copy link
Member

Choose a reason for hiding this comment

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

nit, an extra line break between description and fine detail.

Comment on lines 193 to 198
// override hostnames by hostname
gateway.innerModel().httpListeners().iterator().next().withHostNames(null).withHostname(hostname1);
gateway.update()
.apply();

Assertions.assertEquals(hostname1, gateway.listeners().get(listenerName).hostname());
Copy link
Member

Choose a reason for hiding this comment

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

Do we need this test?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's for confirmation for service response of replacing hostnames with hostname. I wanted to try the other way around but it's much more complicated..

Copy link
Member

Choose a reason for hiding this comment

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

You should be able to replace this case with withHostnames if you support it?

@check-enforcer
Copy link

check-enforcer bot commented Feb 9, 2022

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci

@@ -248,17 +259,23 @@ public ApplicationGatewayListenerImpl withHttps() {
@Override
public ApplicationGatewayListenerImpl withHostname(String hostname) {
this.innerModel().withHostname(null);
Copy link
Member

Choose a reason for hiding this comment

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

Move this line into if (hostname != null) {?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Moved, thanks...

List<String> hostNames = new ArrayList<>();
hostNames.add(hostname);
this.innerModel().withHostNames(hostNames);
}
return this;
}

@Override
public ApplicationGatewayListenerImpl withHostnames(List<String> hostnames) {
this.innerModel().withHostname(null);
Copy link
Member

Choose a reason for hiding this comment

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

Move this line into if (hostname != null) {?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Moved.

XiaofeiCao and others added 3 commits February 9, 2022 11:21
Co-authored-by: Weidong Xu <weidxu@microsoft.com>
…a/com/azure/resourcemanager/network/models/HasHostname.java

Co-authored-by: Weidong Xu <weidxu@microsoft.com>
@XiaofeiCao XiaofeiCao merged commit b3fc31a into Azure:main Feb 9, 2022
@XiaofeiCao XiaofeiCao deleted the mgmt_app_gateway_wildcard_listener branch February 9, 2022 04:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

mgmt, verify wildcard support in network
3 participants