Has anyone managed to use managed identity with Bridge to Kubernetes?
I've been reading these articles:
https://learn.microsoft.com/en-us/visualstudio/bridge/managed-identity?view=vs-2019
https://learn.microsoft.com/en-us/visualstudio/bridge/overview-bridge-to-kubernetes
https://learn.microsoft.com/en-us/visualstudio/bridge/configure-bridge-to-kubernetes
but I cannot get this to work
enableFeatures:
ManagedIdentity
I think there may be a documentation issue because it refers to both KubernetesLocalProcessConfig.yaml and KubernetesLocalConfig.yaml
I've tried both names. If I put the above yaml in KubernetesLocalProcessConfig.yaml I get a yaml serialization error. If I put it in KubernetesLocalConfig.yaml it doesn't seem to do anything so I suspect KubernetesLocalProcessConfig.yaml is the correct name, but I can't find any details of the correct yaml other than on the "Use managed identity with Bridge to Kubernetes" page linked above.
I worked it out by decompiling the extension. It is a documentation issue.
The correct file name is indeed KubernetesLocalProcessConfig.yaml
and the below yaml will work (note the - was missing in the docs)
version: 0.1
enableFeatures:
- ManagedIdentity
SQS client raises Aws::SQS::Errors::NonExistentQueue error when queue is not found. But, why
https://docs.aws.amazon.com/sdk-for-ruby/v3/api/Aws/SQS/Errors.html This doc doesn't mention a thing about it. However, I found it here https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_GetQueueUrl.html#API_GetQueueUrl_Errors. But, this is a general api doc, not specific to Ruby.
Is documentation missing, is there a simple way to find what errors are being thrown?
The docs were likely generated with yard however digging through the git repo I was only able to find version 2x tags and no version 3 tagged anywhere. Only thing I could find was this commit which added the feature specs. Somehow it seems this never made it into the yard code in docs. I'm not sure what version 3 is referring to.
I need to use exactly this method on the adminClusterApi,
client.preparePutIndexedScript()
.setScriptLang("painless")
.setId("script1")
.setSource("script", "_score * doc['my_numeric_field'].value")
.execute()
.actionGet();
I tried the following elastic-search-client version.
* 5.6.1
* 5.3.1
* 5.3.3
but sadly I can't find this method and even the preparePutIndexedScript on the Java Api anymore, does someone have any idea?
according with the documentation this class still exists -> https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/indexed-scripts.html
I found the answer
All the methods related to interacting with indexed scripts have been
removed. The Java API methods for interacting with stored scripts have
been added under ClusterAdminClient class. The sugar methods that used
to exist on the indexed scripts API methods don’t exist on the methods
for stored scripts. The only way to provide scripts is by using
BytesReference implementation, if a string needs to be provided the
BytesArray class should be used.
https://www.elastic.co/guide/en/elasticsearch/reference/5.5/breaking_50_scripting.html#_indexed_scripts_java_apis
would be nice though if the other documentation part that i mentioned would be upgrade was a bit hard to find this.
We decided to give it a spin and we started fresh project using Angular2. So far so good, but at this point we're facing an issue. At this point, what is the proper approach to i18n for Angular2? We've researched a little and found this:
https://github.com/angular/i18n
However last commit is more than 5 months old... Doesn't look like active development.
Anyone tried using angular-translate or angular-gettext? Or maybe with Angular2 it's better to wrap something JS like i18next? Anyone could share their thoughts? Maybe you faced the same problem?
Plunk was updated to Angular 2 Final: https://plnkr.co/edit/4euRQQ. Things seem to work the same as in RC7.
New i18n section has been added to Angular 2 official docs. Basically, it explains in details what happens in the plunkr above.
XLIFF is the only format for translations, no json support.
A translation source file (xliff, xlf) should be created using ng-xi18n tool:
package.json:
"scripts": {
"i18n": "ng-xi18n",
...
}
and
npm run i18n
See the Merge translation section for details about merging a translation into a component template. It's done using SystemJS Text plug-in.
Another example using Gulp http://www.savethecode.com/angular2-i18n-native-support/
Older staff:
Update based on RC7 and links provided by Herman Fransen:
I've made a minimal Plunkr example: https://plnkr.co/edit/4W3LqZYAJWdHjb4Q5EbM
Comments to plunkr:
bootstrap should provide TRANSLATIONS, TRANSLATIONS_FORMAT, LOCALE_ID with values -> setup translations
translatable items in html-templates should use directive i18n
translations are stored in .xlf file. Ties between languages is done through Id, ties with html by a value of <source> tag in xlf
currently xlf files are not used directly; a .ts file is manually created to wrap the content of xlf in an exportable variable. I guess, this should be working automagically in final release (maybe even now).
This is the first officially documented approach I found.
However, it's still barely usable. I see the following issues in the current implementation:
Language is set at bootstrap, unable to change it in run-time. This should be changed in Final.
Id of a translatable item in xlf is generated SHA. Current way to get this id is a bit messy: you create a new translatable item, use it, copy SHA id from error and paste into your i18n.lang.xlf file.
There is a big documentation pull request concerning i18n
Older staff:
Release notes https://github.com/angular/angular/blob/master/CHANGELOG.md have a record
i18n: merge translations 7a8ef1e
A big chunk of i18n was introduced in Angular 2 RC5
Unfortunately, still no documentation available.
Everyone's eager for the official implementation, but this one worked for my use case:
https://github.com/ocombe/ng2-translate
README is fairly thorough, and if you need something real particular (for me it was code-splitting) the code itself isn't too long or hard to read.
Support for i18n is now official in Angular 2 RC6
Official release blog:
https://angularjs.blogspot.nl/2016/09/angular-2-rc6_1.html
A sample of internationalization with Angular 2 RC6
https://github.com/StephenFluin/i18n-sample
More info how the new concept of i18n works in angular2:
https://lingohub.com/blog/2015/03/angular-2-i18n-update-ng-conf-2015
I found another way to implement this using pipe and service
HTML
<!-- should display 'hola mundo' when translate to Spanish -->
<p>{{ 'hello world' | translate }}</p>
TYPESCRIPT
...
// "this.translate" is our translate service
this.translate.use('es'); // use spanish
...
// should display 'hola mundo' when translated to Spanish
this.translatedText = this.translate.instant('hello world');
...
https://scotch.io/tutorials/simple-language-translation-in-angular-2-part-1
https://scotch.io/tutorials/simple-language-translation-in-angular-2-part-2
There is an official support for i18n in Angular.io here:
https://angular.io/docs/ts/latest/cookbook/i18n.html
But! As mentioned in docs:
You need to build and deploy a separate version of the application for
each supported language!
That makes this feature useless in most cases ...
Unless you will use it without CLI as described here:
https://devblog.dymel.pl/2016/11/03/angular2-and-i18n-translate-your-app/
I am putting together a POC and the official documentation is cumbersome to say the least, so I tried ngx-translate http://www.ngx-translate.com/ and I literally had the hello world working in a few minutes, there are few caveats:
I've read of people complaining about performance, because of the pipes, but reading the github issues, it seems that it is getting resolved
It is only for i18n or Translations it does not deal with i10n or Localization
There are few warning errors with Angular4 but it works anyways
long story short I liked ngx-translate if you have a small app and only need translation
I personally wanted Localization, so I am looking at
https://github.com/robisim74/angular-l10n
. It looks pretty good, but I haven't tested, so I'll let you know later, or you guys can go and we all try
I was wondering if there is a javadoc style API reference for the boost libraries?
I have noticed that there are class descriptions with these type of urls:
http://www.boost.org/doc/libs/1_52_0/doc/html/boost/program_options/typed_value.html
Whereas documentation of particular libraries is at the following:
http://www.boost.org/doc/libs/1_52_0/doc/html/program_options/
Notice the html/boost subdirectory. Considering this, perhaps there is an organized/categorized API index for these raw indexes:
http://www.boost.org/doc/libs/1_52_0/doc/html/boost
http://www.boost.org/doc/libs/1_52_0/doc/html/boost/program_options/
Boost is a collection of many different libraries, by many different authors. There is no comprehensive documentation. Several of the libraries provide API documentation as you have already noted. I think the Asio API documentation is particularly well written.