</span>
						</div>
					</div>
					<div class="text-center">
						<button type="submit" name="changePassword"
							class="btn btn-primary btn-block"
							value="<la:message key="labels.login.update"/>">
							<em class="fa fa-pencil-alt">
							<la:message key="labels.login.update" />
						</button>
					</div>
				</la:form>
			</div>
		</div>
	</div>

							<la:message key="labels.profile.back" />
						</la:link>
						<button type="submit" name="changePassword"
							class="btn btn-success"
							value="<la:message key="labels.profile.update"/>">
							<em class="fa fa-pencil-alt">
							<la:message key="labels.profile.update" />
						</button>
					</div>
				</la:form>
			</div>
		</div>
	</div>

                                    <em class="fa fa-plus-circle">
                                    <la:message key="labels.web_crawling_button_create_job"/>
                                </la:link></c:if>
                            </div>
                        </div>
                    </div>
                </div>
            </la:form>

'environments', allowing applications to select a set of control plane settings and components. While the entire mesh respects the same APIs and config, apps may target different 'environments' which contain different instances and variants of Istio. - Better security: separate Istio components reside in different namespaces, allowing different teams or roles to manage different parts of Istio. For example, a security team would maintain the root CA and policy, a telemetry team may only have access to...

                                                                >
                                                                    <em class="fa fa-trash">
                                                                    <la:message key="labels.crud_button_delete"/>
                                                                </button>

                                                                data-dismiss="modal">
                                                            <la:message key="labels.crud_button_cancel"/>
                                                        </button>
                                                        <button type="submit" class="btn btn-outline-light"

                                <button type="submit" class="btn btn-outline-secondary" name="index"
                                        value="<la:message key="labels.wizard_button_cancel"/>">
                                    <la:message key="labels.wizard_button_cancel"/>
                                </button>
                                <button type="submit" class="btn btn-primary"

                                                            <button type="button" class="close" data-dismiss="modal"
                                                                    aria-label="Close">
                                                                <span aria-hidden="true">×</span>
                                                            </button>
                                                        </div>

                                    <button type="submit" class="btn btn-primary"
                                            name="crawlingConfigForm"
                                            value="<la:message key="labels.wizard_start_button"/>">
                                        <em class="fa fa-arrow-circle-right">
                                        <la:message key="labels.wizard_start_button"/>

name: Feature Enhancement Request
description: I want to make an existing feature better
labels: ["type=enhancement"]
body:
  - type: markdown
    attributes:
      value: >
        Filing feature requests is one of the most popular ways to contribute to Guava.


        Be aware, though: most feature requests are not accepted, even if they're suggested by
        a full-time Guava team member. [Feedback](https://stackoverflow.com/a/4543114) from our