I'm doing a test to use GCP Data Catalog (DataPlex) to document tables from Big Query.
I'm doing in a dev project, in the future, I'd like transfer data that I documented (description of columns, overview of table) from dev project to prod project?
Is it possible?
https://github.com/mesmacosta/datacatalog-util is an export/import utility that lets you achieve what I believe you are looking for, provided that you use tags to store these descriptions?
Related
It is possible to duplicate a complete google cloud project with minimal manual interaction?
The purpose of this duplication is to create a white label.
In case there is no "easy" way, can you tell me what tools I can use to duplicate my existing project?
You can use terraformer to reverse engineering your infrastructure. You can generate TF file that you will be able to use with terraform in the other project.
However, it's only the infrastructure. Your VM configuration, your app contents, your data (file and database) content aren't duplicated! No magic tools for this.
I have almost 10+ Projects created in Watson Data Platform.
I created a Data Catalog and added some data assets csv.
Now i am trying to add the dataset to existing projects.
But it only shows one project out of my 10 projects.
Can you please help?
Thanks,
Charles.
I found out following:-
This screen lists/pulls all projects that are restricted, all projects that are bluemix COS types, all projects you have permissions to.
Restricted means Under Project Settings -> Project Scope should be restricted to who can collaborate should set to Yes. The same option is being asked when you create the project. It restricts only users who are part of your Bluemix Organization to be added as collaborators.
Also the project should be using Cloud Object Storage as Storage.
Hope others find this useful.
Thanks,
Charles.
I'm having a class with stuff that changes per build. For the debug build some network calls are different because of another server, release and mock too.
In Android I use flavors and put in each flavor a file with the same name but the code is different.
I'm searching for the same possibility in xCode. I've seen tutorials like this but thats doing it via plists. But it's not working for classes.
There are so many ways to do this.
My personal favorite is to use multiple Targets. I won't go into real detail here as a simple google search should reveal plenty of information on how to create and work with multiple targets.
I prefer targets because it is so simple to switch between them depending upon your needs and the fact that you can have each of the targets on one device as needed. For example you can have a current production version of your app on the device along with your latest dev and QA versions as well.
An alternative would be to use "Categories" - again google should get you plenty of information to implement.
Use the category to extend your class with the specific information you need for each environment. Create multiple iterations of your category (one for each group of settings) and use a pre-build script to copy the desired instance into your project.
We are just beginning development and implementation for dynamics crm 2011 on premises. Is it possible to implement automation for code check-in to promote code from development to test systems? It looks like this would involve export/import of unmanaged solutions containing the development code that was checked in. I have not been able to find APIs around this functionality.
If that is not possible, how close can you get? It looks like there are APIs to automate the uploading of web resources and plug-ins (e.g. webresourceutility in the sdk), but the web resources still need to be manually linked to the form they are to be used on (in the case of javascript etc). Has anyone made progress in automating parts of their CRM environments?
for reference, we're using vs 2010 & tfs 2010 using MSuild for current continuous integration.
We have a few techniques that provides us a very solid CI structure.
Plugins
All our Plugins are CI Compiled on Check-In
All plugin code we write has self-registration details as part of the component.
We have written a tool which plays the Plugins to the database, uninstalling the old ones first based on the self-registration
details.
Solution
We have an unmanaged solution in a Customisation organisation which
is clean and contains no data. Development is conducted out of this
organisation. It has entities, forms, Jscript, Views, Icons, Roles,
etc.
This Customisation database has all the solutions we've imported from 3rd parties, and customisations are made into our solution which is the final import into a destination organisation.
The Solution is exported as managed and unmanaged and saved into
TFS
We store the JScript and SSRS RDLs in TFS and have a custom tool
which plays these into the customisation database before it is
exported.
We also have a SiteMap unmanaged Solution which is exported as unmanaged (to ensure we get a final resultant Sitemap we are after)
Deployment
We have a UI and Command Line driven tool which does the following :-
Targets a particular Organisation
Imports the Customisation managed solution into a selected environment. e.g. TEST. Additionally imports the unmanaged Sitemap.
Uninstalls the existing solution which was there (we update the solution.xml file giving it a name based on date/time when we import)
Installs/Uninstalls the Plugin Code
Installs any custom SQL scripts (for RDLs)
Re-enables Duplicate Detection Rules
Plays in certain meta-data we store under source control. e.g. Custom Report entity we built which has attachments and XML configuration.
It isn't entirely perfect, but via command line we refresh TEST and all the Developer PCs nightly. It takes about 1 hour to install and then uninstall the old solution per organisation.
We use CI extensively for Dynamics CRM. For managing solutions, I would recommend using a "clean" Dynamics CRM implementation which will be the master for your solutions and also for your "domain data". See http://msdn.microsoft.com/en-us/library/microsoft.crm.sdk.messages.importsolutionrequest.aspx for importing solutions. Also check out - http://msdn.microsoft.com/en-us/library/hh547388.aspx
I have a database project which uses link servers in several of the views and stored procedures.
According to Microsoft, Visual Studio 2010 database projects do not explicitly support link servers, but you can kind of hack it using References and SQLCMD variables:
http://msdn.microsoft.com/en-us/library/bb386242.aspx
My database (the database itself) has a link server conenction to a Warehouse database. The Warehouse database project is stored in a separate Team Project Collection.
Is there any way to add the Warehouse project as a reference in my project?
The following article explains how to use reference variables in a database project.
http://msdn.microsoft.com/en-us/library/bb386242.aspx
This is necessary when you are referring to a database that is not in the same solution (see the first chart, second row).
In my case, I will probably have separate solutions for each different business environment (internal apps, external apps, warehouse, etc.). Each of these solutions will have several databases. But the databases will need to refer to databases that are not in the same solution (ex., an internal DB might have stored procedures that pull data from an external DB).
In this case, I think the best solution is to refer to the .dbschema file that is generated when the project is built. You can configure a nightly build for each project, and have the build output be copied to a specific shared drive location. You could then point any database project to any other database’s schema by adding a database reference (described in the above article) to the .dbschema ( on the shared drive) for the database.
If you wanted to make it more sophisticated, you could modify the build template to copy the necessary .dbschema files from the build output into each project and check them in.
In the case where the database does not have a project and is not being actively changed, it will be necessary to create a temporary database project for the database so you can build a .dbschema file. The built .dbschema file can then be checked in to the dependent project, and you won’t have to generate it ever again unless it changes.
I’ll do my best at an example…
Problem:
Project ABC depends on the data warehouse, and on project XYZ. Project XYZ is in source control under a different solution, but the Warehouse is not in source control.
Solution:
Create a nightly build for project XYZ
Configure the build output directory to go to a shared drive
Create a custom build template for project ABC that will copy the XYZ.dbschema file in to the ABC project and check it in
In project ABC, right-click on “Database References” and add a reference to XYZ, specifying the XYZ.dbschema file (instead of the XYZ database project, which is outside the solution)
Create the reference variables to the XYZ project (not sure this is necessary…)
Replace references to XYZ in stored procs & views with the reference variables you created in the previous step (not sure this is necessary…)
Now the references in ABC to XYZ should resolve.
Create a new database project (this can be a temporary, throw-away project)
Have it pull the definition from the Warehouse (right click the project and select “Import from database”)
Build the project
Copy the Warehouse.dbschema file from the build output into the ABC project
In project ABC, right-click on “Database References” and add a reference to the Warehouse.dbschema file
Create reference variables for the Warehouse
Replace references to the Warehouse with the reference variables
Now the references in ABC to the Warehouse should resolve.
I don’t know if it will work just like that, but that is the theory. Hope it helps…